Hardware-based credential distribution

ABSTRACT

This document describes various techniques for distributing credentials based on hardware profiles. A resource access request including a hardware profile is transmitted to a remote entity having access to a previous hardware profile and a credential useful to access a resource is received if at least a portion of the hardware profile matches the previous hardware profile.

BACKGROUND

Credentials allow a service to authenticate a client before providing resources or sharing data with the client. Services usually distribute verifiable credentials to clients to allow the client to access the resources or data over a network. Credentials are not infinite, however, and should only be distributed to actual users of the service. Arbitrary distribution of credentials can result in exploitation or interruptions of services, such as denial of service attacks by malicious entities.

To limit distribution of credentials many services rely on human-verification methods. These human-verification methods use logins, passwords, and/or challenge response tests to verify the client's identity when a service is accessed. While these human-verification methods help to limit credential distribution to clients associated with human users, they compromise a user's computing experience.

SUMMARY

This document describes various techniques for distributing credentials based on hardware profiles. These techniques may validate a request for a resource by matching a hardware profile of the requesting entity to a previous hardware profile associated with that requesting entity. Once validated, the techniques distribute a credential for accessing the resource. By so doing, the techniques protect the resource from exploitation or attack without compromising a user's computing experience.

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanying figures. In the figures, the left-most digit of a reference number identifies the figure in which the reference number first appears. The use of the same reference number in different instances in the description and the figures may indicate similar or identical items.

FIG. 1 illustrates an example environment in which these techniques may be performed.

FIG. 2 illustrates an example computing device of FIG. 1 in more detail.

FIG. 3 is a flow diagram depicting an example process for accessing a resource with a credential distributed based on a hardware profile.

FIG. 4 is a flow diagram depicting an example process for distributing a credential based on a hardware profile.

FIG. 5 is a flow diagram depicting an example process for granting access to a resource based on an indication of a validity of a request.

DETAILED DESCRIPTION Overview

This document describes various techniques for distributing credentials based on hardware profiles. These techniques can improve a user's computing experience by forgoing a login, password, and/or response challenge, though these techniques can be used in conjunction with human-verification methods for additional security.

Example Environment

FIG. 1 is an illustration of an example environment 100 having a computing device 102, server 104, and communication network 106, through which computing device 102 and server 104 may communicate. Generally, computing device 102 requests access to a resource of server 104 through communication network 106. In some embodiments, a secure communication channel is established between computing device 102 and server 104 over communication network 106 for providing resources and/or exchanging trusted data.

Computing device 102 can be any device capable of communicating over a network (e.g., communication network 106), accessing resources of a service, and exchanging trusted data. Computing device 102 is illustrated, by way of example and not limitation, as one of a smartphone 108, a laptop computer 110, set-top box 112, desktop computer 114, or tablet computer 116. Communication network 106 may include any suitable network such as the Internet, a local-area network, a wide-area network, a wireless-network, a personal-area network, a dial-up network, and/or a USB bus, to name a few.

Server 104 can be any computing device having resources and/or hosting a service for managing the resources, such as objects, data, functionalities, and the like. The service of server 104 requires authentication of a client before sharing a resource with the client requesting access to the resource. In some cases, authentication may be direct with computing device 102 or brokered through a third party associated with both server 104 and computing device 102 (not shown). A resource of server 104 is typically referenced by a Uniform Resource Locator (URL) or Universal Resource Identifier (URI). A URL or URI is used by a client, such as computing device 102, for initiating access of the resource. In other cases, a resource may be referenced by an abstract domain in extensible markup language (XML) such as a namespace.

FIG. 2 illustrates an example computing device 102 of FIG. 1 in more detail. Computing device 102 includes processor(s) 202, computer-readable media (CRM) 204, and network interface 206. Network interface 206 allows computing device 102 to communicate over communication network 106 and may include a unique media access control (MAC) address (not shown). Computer-readable media 204 contains memory media 208, storage media 210, and resource access manager 212, which is described as part of the processes discussed below.

Memory media 208 can include dynamic random access memory (DRAM) 214, static random access memory (SRAM) 216, read-only memory (ROM) 218, or any combination thereof. Memory media 208 may be fixed or modular (flexibly configured) providing various configurations and/or capacities of memory for computing device 102. For instance, DRAM 214 may be user accessible, allowing a user to increase an amount of DRAM 214 present in computing device 102. Alternately or additionally, memory media 208 may include information relating a manufacturer, data rate, and/or capacity of memory device(s) of computing device 102. In some instances, DRAM 214 includes a serial presence detect integrated circuit (not shown) presenting information relating to a data rate and capacity of DRAM 214.

Storage media 210 can include hard disk drive (HDD) 220 and/or flash 222. Storage media 210 is internal and/or external (but local) computer-readable storage media and is capable of storing data. Hard disk drive 220 or flash 222 can be configured as individual storage volumes or as multiple drives of a redundant array of independent disks (RAID) volume. Alternately or additionally, storage media 210 can include information relating to a manufacturer, model number, serial number, and/or a capacity of a particular storage media device. For instance, hard disk drive 220 may include a model number, serial number, and capacity information detectable by a host device or a component of a host device.

Generally, any of the techniques and abilities described herein can be implemented using software, firmware, hardware (e.g., fixed-logic circuitry), manual processing, or any suitable combination of these implementations. The example computing device 102 generally represents software, firmware, hardware, or any combination thereof. In the case of a software implementation, for instance, resource access manager 212 represents computer-executable instructions (e.g., program code) that perform specific tasks when executed on a processor (e.g., CPU or CPUs). The program code can be stored in one or more computer-readable media devices, such as memory media 208 and/or storage media 210. The features and techniques described herein are platform-independent, meaning that they may be implemented on a variety of commercial computing platforms having a variety of processors.

Example Processes

The following discussion describes techniques for distributing credentials based on hardware profiles. These techniques can be used instead of or in addition to human-verification methods. When used in addition to human-verification methods, these techniques provide additional security for credential distribution. When used instead of human-verification methods, these techniques forgo often-annoying or time-consuming user-dependent activities.

By way of example, assume computing device 102 transmits a resource access request including a unique identifier and a current hardware profile to server 104 over communication network 106. Server 104 receives the unique identifier and hardware profile, determines whether or not the hardware profile matches at least a portion of a stored hardware profile associated with the unique identifier, and, if it matches, sends a credential useful to access a resource to computing device 102.

Aspects of these processes may be implemented in hardware, firmware, software, or a combination thereof. These processes are shown as sets of blocks that specify operations performed, such as through one or more entities or devices, and are not necessarily limited to the order shown for performing the operations by the respective blocks. In portions of the following discussion reference may be made to environment 100 of FIG. 1 as well as entities of environment 100 illustrated in FIG. 2.

FIG. 3 is a flow diagram depicting an example process 300 for accessing a resource with a credential distributed based on hardware profiles. Block 302 transmits a resource access request including a unique identifier and a current hardware profile to a remote entity. In some cases, the resource access request is just the unique identifier and the current hardware profile. The remote entity has access (locally, remotely, or via proxy) to a previous hardware profile associated with the unique identifier. In some instances, the unique identifier is associated with the previous hardware profile during a past attempt to access a resource or during a secure registration process.

The current hardware profile includes information relating to hardware components or a hardware configuration of a computing device. This profile can be generated by an application programming interface (API) based on information relating to hardware of a computing device, such as serial numbers, model numbers, and/or parameters of hardware components of the computing device.

The unique identifier is any certificate, token, identification data, or combination thereof that uniquely identifies a computing device. In some cases, the unique identifier is digitally signed or encrypted with a private key and/or shared key to ensure authenticity. This unique identifier may be received during a secure registration process that associates the unique identifier with a hardware profile. For instance, the unique identifier may be a software license validation (SLV) certificate received during secure registration with an SLV server. During this secure registration, a hardware profile sent to the SLV server is associated with the SLV certificate.

By way of example, consider process 300 in the context of environment 100. Resource access manager 212 generates a current hardware profile of laptop computer 110 based on information relating to DRAM 214, HDD 220, and Network Interface 206. This current hardware profile includes information relating to a manufacturer and a capacity (or amount) of DRAM 214, a serial number and model number of HDD 220, and a MAC address of network interface 206.

Here assume that resource access manager 212 is attempting to access a software update of server 104. To do so, resource access manager 212 transmits a resource access request including a unique identifier and the current hardware profile to server 104 over communication network 106.

Block 304 receives a credential useful to access a resource from the remote entity if the current hardware profile matches at least a portion of the previous hardware profile. The credential is useful to access a resource directly or access a service managing resources, functionalities, and/or data. In the context of the present example, assume that the manufacturer and capacity (or amount) of DRAM 214 and the MAC address of network interface 206 of the current hardware profile match corresponding information of a previous hardware profile associated with the certificate. Resource access manager 212 receives, from server 104, a credential useful to access the software update resource responsive to a portion of the current hardware profile matches the previous hardware profile.

Optionally, at block 306, a resource is accessed using the received credential. The resource may be accessed directly or through a service managing the resource and/or data. In some cases, the resource is a functionality provided by the service, such as messaging, synchronizing data, or trusted data exchange. Concluding the present example, resource access manager 212 accesses the software update resource of server 104 using the received credential and downloads a software update over communication network 106.

FIG. 4 is a flow diagram depicting an example process 400 for distributing a credential useful to access a resource based on hardware profiles. Block 402 receives a resource access request including a unique identifier and a hardware profile. The unique identifier may be any of those noted above, such as a certificate, token, or identification data or combination thereof that uniquely identifies a remote entity. In some cases, the unique identifier is digitally signed or encrypted with a private key unknown to the remote entity to prevent tampering and/or alteration of the unique identifier. For instance, the unique identifier may be an SLV certificate encrypted with a private key known to an SLV server which issued the certificate.

The hardware profile contains information relating to the remote entity's hardware, such as a collection of serial numbers, model numbers, and/or parameters of hardware components. For instance, the hardware profile can include information about a manufacturer, model number, serial number and a capacity of a hard disk drive.

Consider process 400 in the context of the above-mentioned example. Here server 104 receives a resource access request from resource access manager 212 of laptop computer 110 through data communication network 106. The resource access request includes a hardware profile of laptop computer 110 and a unique identifier in the form of certificate encrypted with a private key known to server 104. The hardware profile of laptop computer 110 includes information relating to a manufacturer and a capacity (or amount) of DRAM 214, a serial number and model number of HDD 220, and a MAC address of network interface 206.

Block 404 determines that the hardware profile matches at least a portion of a stored hardware profile associated with the unique identifier. The stored hardware profile may be stored during a secure registration or license validation process. For instance, a hardware profile received during an SLV process may be stored and associated with an SLV certificate.

In some cases, all of the information contained in the hardware profile matches the information contained in the stored hardware profile associated with the unique identifier. In other cases, where only a portion of the hardware profile matches the stored hardware profile, fuzzy-logic may be employed to determine that the hardware profile sufficiently, but not entirely, matches the stored hardware profile.

A match can be determined using fuzzy-logic even though information relating to a HDD of the hardware profile does not match information relating to a HDD of the stored hardware profile. A matching algorithm employing fuzzy-logic provides flexible matching, allowing a match to be determined for a computing device that has new and/or different hardware components due to repairs and/or upgrades.

This matching algorithm, for example, may determine that the hardware profile is sufficiently similar when two of three hardware component parameters match. The matching algorithm may determine a sufficient match based on various criteria, such as serial numbers that are unlikely to change, while other non-matching serial numbers are acceptable for hardware often altered or replaced, such as external hard drives or non-integrated displays, but not motherboards or processors.

Continuing the ongoing example, server 104 decrypts the certificate using a private key to identify laptop computer 110. Server 104 then determines that at least a portion of the hardware profile of laptop computer 110 matches a stored profile that is associated with the certificate included in the resource access request. Here assume that a user of laptop computer 110 has replaced HDD 220 of laptop computer 110 due to a failure of a previous HDD.

In the context of the present example, a matching algorithm of server 104 employing fuzzy-logic determines that the hardware profile of laptop computer 110 sufficiently matches the stored hardware profile based on the information relating to the manufacturer and the capacity (or amount) of DRAM 214 and the MAC address of network interface 206.

Block 406 transmits a credential to the remote entity useful to access a resource. The credential may be useful to access a resource directly or access a service managing the resource and/or providing functionality related to the resource. In some cases, a credential distribution limit or rule is consulted prior to transmitting the credential limiting distribution of credentials. In some instances, the credential distribution limit is associated with the unique identifier to limit credential distribution to an entity (or entities claiming to be) associated with the unique identifier.

Credential distribution can be limited to a total number of credentials distributed, a rate of credential distribution, or a frequency of credential distribution or any combination thereof. For instance, credential limits associated with a unique identifier may only allow one credential to be distributed every 10 seconds with a total limit of 50 distributed credentials.

Continuing the present example, assume that server 104 has a credential distribution limit of 50 total credentials per unique identifier. Also assume that one credential has been previously issued in association to the certificate included in the resource access request received from laptop computer 110. Here, server 104 consults the credential distribution limit and determines that a credential can be issued to laptop computer 110. Concluding the present example, server 104 increments a credential distribution count associated with the unique identifier and transmits a credential useful to access a software update to laptop computer 110 over communication network 106. This is but one way in which the techniques may limit credential distribution to computing devices of actual users of a service.

FIG. 5 is a flow diagram depicting an example process 500 for granting access to a resource. Block 502 receives a request for resource access including a unique identifier and a hardware profile, such as those unique identifiers and hardware profiles mentioned above.

Consider process 500 in the context of environment 100. Here server 104 receives a resource access request from resource access manager 212 of laptop computer 110 over communication network 106. Assume that the resource access request includes a certificate encrypted with a private key and a hardware profile of laptop computer 110. Also assume that server 104 is hosting a software update service, and that resource access manager 212 of laptop computer 110 is attempting to access the software update service. In the context of the present example, server 104 does not have a private key for decrypting the certificate included in the resource access request.

Block 504 forwards the unique identifier and hardware profile to a request-validating entity having access to a historical hardware profile associated with the unique identifier. The historical hardware profile includes information previously collected relating to hardware components or a hardware configuration of a computing device. In some cases, the historical hardware profile is received from a computing device during a secure registration process. In such a case, the unique identifier may have been issued to the computing device and associated with the received hardware profile. For instance, the unique identifier and hardware profile may be forwarded to an SLV server having a stored historical profile associated with an SLV ticket encrypted with a private key.

The request-validating entity may also have access to a private and/or shared key useful to decrypt an encrypted unique identifier. In some cases, the request-validating entity decrypts a certificate, token, or digital signature to expose information uniquely identifying a computing device, such as an SLV server having a private key decrypting and verifying an SLV ticket included in the request.

In the context of the present example server 104 forwards the certificate encrypted with the private key and the hardware profile of laptop 110 to a remote request-validation server (not shown). Here, assume that the request-validation server has a private key capable of decrypting the certificate and a historical hardware profile associated with the certificate.

Block 506 receives an indication of a validity of the request if the request-validating entity determines that the hardware profile of the remote entity matches at least a portion of the historical hardware profile. This indication of validity may include identification information relating to the remote entity, such as information identifying the remote entity as an owner of a software product or as a subscriber to a service. For instance, an indication of the validity of the request can be received from an SLV server when at least a portion of the hardware profile of the remote entity matches a historical hardware profile associated with an SLV ticket.

Continuing the present example, server 104 receives an indication of the validity of the request when the request-validation server determines that the hardware profile of laptop computer 110 matches at least a portion of the historical hardware profile associated with the certificate. The indication of the validity of the request also includes identification information that identifies laptop computer 110 as a subscriber of the software update service of server 104.

Block 508 grants access of the resource to the remote entity based on the indication of the validity of the request. In some cases, a credential useful to access the resource is transmitted to the remote entity. The credential is useful to access a resource directly or access a service managing the resource and/or providing functionality related to the resource. Furthermore, access to the resource may be limited or denied based on identification information relating to the remote entity. For example, access may be limited to updates of a particular software product based on information that identifies the remote entity as an owner of that software product.

Concluding the present example, server 104 grants access of the software update service to laptop computer 110 based on the validity of the request. The access granted is limited by server 104 based on the identification information that identifies laptop computer 110 as a subscriber to that service.

CONCLUSION

This document describes various techniques for distributing credentials based on hardware profiles. By so doing, these techniques improve security and/or a computing experience of a user accessing a resource via a service. Credentials useful for accessing a resource can be provided to a user without querying the user for a login, password, and/or response challenge. Although the invention has been described in language specific to structural features and/or methodological acts, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as example forms of implementing the claimed invention. 

1. A method comprising: transmitting a resource access request to a remote entity, the resource access request including a unique identifier and a current hardware profile, the remote entity having access to a previous hardware profile associated with the unique identifier; and receiving a credential useful to access a resource of the remote entity if the current hardware profile matches at least a portion of the previous hardware profile.
 2. The method as recited in claim 1, further comprising generating the current hardware profile.
 3. The method as recited in claim 1, wherein the current hardware profile includes information relating to hardware of a computing device.
 4. The method as recited in claim 3, wherein the information relating to the hardware of the computing device includes a collection of serial numbers, model numbers, or parameters of hardware components of the computing device.
 5. The method as recited in claim 1, wherein the unique identifier was received during a secure registration process.
 6. The method as recited in claim 5, wherein the previous hardware profile was transmitted to an entity associated with the issuance of the unique identifier.
 7. The method as recited in claim 1, wherein the unique identifier is a certificate digitally signed or encrypted with a private key.
 8. The method as recited in claim 1, wherein the resource is a resource of a service and further comprising accessing the service using the received credential.
 9. A method comprising: receiving a resource access request from a remote entity, the resource access request including a unique identifier of the remote entity and a hardware profile of the remote entity; determining that the hardware profile matches at least a portion of a stored hardware profile associated with the unique identifier; and transmitting a credential to the remote entity useful to access a resource.
 10. The method as recited in claim 9, wherein the hardware profile of the remote entity includes a collection of serial numbers, model numbers, or parameters of hardware components.
 11. The method as recited in claim 9, wherein determining that the hardware profile matches at least a portion of a stored hardware profile associated with the unique identifier employs a fuzzy-logic algorithm.
 12. The method as recited in claim 9, further comprising determining if a credential distribution limit associated with the unique identifier has been exceeded.
 13. The method as recited in claim 12, wherein the credential distribution limit is based on a total number of credentials distributed, a rate of credential distribution, or a frequency of credential distribution.
 14. The method as recited in claim 9, wherein the unique identifier is electronically signed or encrypted with a private key unknown to the remote entity.
 15. A method comprising: receiving a request for resource access from a remote entity, the request including a unique identifier and a hardware profile of the remote entity; forwarding the unique identifier and the hardware profile to a request-validating entity having access to an historical hardware profile associated with the unique identifier; receiving an indication of a validity of the request if the hardware profile of the remote entity matches at least a portion of the historical hardware profile; and granting access of the resource to the remote entity based on the indication of the validity of the request.
 16. The method as recited in claim 15, wherein the indication of validity includes identification information relating to the remote identity.
 17. The method as recited in claim 16, further comprising limiting access to the resource based on the identification information relating to the remote entity.
 18. The method as recited in claim 15, wherein the unique identifier is a certificate digitally signed or encrypted with a private key.
 19. The method as recited in claim 15, wherein granting access of the resource to the remote entity includes transmitting a credential to the remote entity useful to access the resource.
 20. The method as recited in claim 15, wherein the resource is a service requiring authentication. 